v3.13.0 #92
Merged
v3.13.0 #92
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DatabaseMapperExenabling extended/explicit mapping where performance is critical versus existing that uses reflection and compiled expressions; can offer up to 40%+ improvement in some scenarios.AddMappers<TAssembly>()andAddValidators<TAssembly>()extension methods now also support two or three assembly specification overloads.WorkState.UserNamehas been added to enable the tracking of the user that initiated the work; this is then checked to ensure that only the initiating user can interact with their own work state.ReferenceDataOrchestrator.GetByTypeAsynchas had the previous sync-over-async corrected to be fully async.ExistsandExistsAsyncwhich expect a non-null resultant value have been renamed toValueExistsandValueExistsAsyncto improve usability; also they areIResultaware and will act accordingly.ETagHTTP handling has been updated to correctly output and expect the weakW/"xxxx"format.ETagGeneratorimplementation has been further optimized to minimize unneccessary string allocations.ValueContentResultwill only generate a response header ETag (ETagGenerator) for aGETorHEADrequest. The underlying resultIETag.ETagis used as-is where there is no query string; otherwise, generates as assumes query string will alter result (i.e. filtering, paging, sorting, etc.). The resultIETag.ETagis unchanged so the consumer can still use as required for a further operation.SettingsBasehas been optimized. The internal recursion checking has been removed and as such an endless loop (StackOverflowException) may occur where misconfigured; given frequency ofIConfigurationusage the resulting performance is deemed more important. Additionally,prefixesare now optional.settings.GetValue<T>("NamedProperty")) and it using reflection to find before querying theIConfigurationhas been removed. This was not a common, or intended usage, and was somewhat magical, and finally was non-performant.